HTTPEnableConnectorHeaders=1
Yes, this will cause all kinds of problems
if not running IHS in front of Domino in self contained mode or running
with the WAS Websphere Web Connectors (reverse proxy modules). This
parameter indicates that we should look for special context headers and
use those headers for the context of the SSL connection between the Browser
and IHS. If the SSL context header is not present we think the connection
between IHS and the browser is not SSL and can get into an infinite redirection
loop.
The Domino SSL network connection has
no effect on whether the connection is SSL or not with this ini. The connection
may be normal http between IHS and the Browser and SSL between IHS and
Domino (not a likely configuration, but possible).
That explains the behavior you are seeing, and why we were not reproducing
in the lab,
This ini should only be set if running Domino in back
of the WAS Reverse Proxy Plugins/modules. It is not used/needed for
the case where Domino runs IHS for the TLS stack locally on the same machine,
and it should never be used when Domino is a contacted
directly by browser clients.
Thanks for the info, this is something we should tech note and/or make
support aware of in case others run into this.